Remote control for implantable medical device

ABSTRACT

A system and method for modifying the parameters of an implantable medical device includes an implantable medical device that communicates with a remote control device that, in turn, communicates through the browser of a computer or any other device capable of using mark-up language protocol. The computer optionally communicates with other computers and/or devices through a network.

The present application claims the benefit of U.S. Provisional Application Ser. No. 60/477,604, filed Jun. 11, 2003, which application is herein incorporated by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates to implantable medical devices, and more particularly, to remote control devices for communicating with an implantable medical device and a computer.

BACKGROUND OF THE INVENTION

Current implantable medical devices such as pacemakers, cochlear implants, spinal cord stimulators, and deep brain stimulators, are typically programmed by a specially designed remote control device, or telemetry system, that contains a computer and a radio or magnetic device to communicate with the implantable device. Implantable sensor systems and infusion pumps also require telemetry systems. Implantable sensor systems sense the level of various substances within the body, such as medications, hormones, neurotransmitters, electrolytes, enzymes, gases, and glucose.

The remote control device's computer contains a specific program designed to control the particular type of implant. Some of the remote control devices are complete in themselves. But, some other remote control devices require a larger computer (sometimes called a special-purpose programmer, Clinician's Programmer, or Fitting Station) to configure the remote control parameters, such as speech processing strategies or the adjustability limits of the remote control by the patient.

Clinician's Programmers and their accompanying software programs are very expensive. As the variety of medical devices increases, clinicians are required to stock and track an increasing variety of special purpose devices. A clinician who does not have the appropriate special purpose device cannot offer any assistance to a patient whose treatment requires the device. As a result, patients are restricted to seeking treatment from a limited number of clinics. Patients who must travel long distances to reach one of these qualified clinics are unduly burdened with added expense and inconvenience.

Therefore, a need exists for an implantable medical device remote control system that may be controlled by a clinician without the use of a complex and expensive Clinician's Programmer or Fitting Station.

SUMMARY OF THE INVENTION

The present invention addresses the above and other needs by providing a system for fitting, or altering the parameters of, implantable medical devices using only the patient's own remote control and a general purpose computer equipped with a web browser and network connection, or other communication means, to link to the patient's remote control. Optionally, once a web page from the remote control device is delivered to the browser of the clinician's computer, the clinician can permit a remote user, such as another clinician or the technical support staff of the implant manufacturer, to view and control the parameters displayed on the web page from a remote location. Information in the clinician's browser can be uploaded to a remote site, or server, to be viewed or altered by others.

The present invention eliminates the need for clinicians to be equipped with separate computers and/or software used to manage or control the parameters of the implant. The present invention allows a patient to simply present his remote control device to the clinician, and the clinician is then able to interrogate and intervene as required.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects of the present invention will be more apparent from the following more particular description thereof, presented in conjunction with the following drawings wherein:

FIG. 1 is a diagram that illustrates a communication system provided by the present invention;

FIG. 2 is a more detailed diagram of the communication system of FIG. 1;

FIG. 3 is a diagram of computer software components of a remote control device used with the present invention; and

FIG. 4 is a flow chart illustrating steps for using a system of the present invention.

Corresponding reference characters indicate corresponding components throughout the several views of the drawings.

DETAILED DESCRIPTION OF THE INVENTION

The following description is of the best mode presently contemplated for carrying out the invention. This description is not to be taken in a limiting sense, but is made merely for the purpose of describing the general principles of the invention. The scope of the invention should be determined with reference to the claims.

Recently, others have developed communications systems similar to the present invention in order to monitor and control the behavior of implantable medical devices. For example, U.S. Pat. No. 6,442,432 (issued Aug. 27, 2002) (the '432 patent), incorporated herein by reference, teaches a general purpose computer loaded with a software application that allows the computer to communicate with an interface medical unit connected to the general purpose computer. The interface medical unit also communicates with an implantable medical device (Col. 13, lines 58-63). The '432 patent also teaches an interface medical unit that downloads instructions from a remote expert server and sends the instructions to a remote implantable medical device. Col. 13, lines 10-12. Nevertheless, the '432 patent fails to teach an interface medical unit loaded with server software capable of delivering data to the browser of a general purpose computer.

U.S. Pat. No. 6,497,655 (issued Dec. 24, 2002) (the '655 patent), also incorporated herein by reference, provides a programmer or interface medical unit in communication with an implantable medical device. The programmer or interface medical unit is an interface between the implantable medical device and a remote web-based expert data center (Col. 11, lines 23-27; cols. 15-16, lines 59-18; col. 16, lines 62-64). The remote web-based expert data center has several complex programming software modules that permit a physician to provide clinical care and therapy to a patient (Cols. 21-24, claims 1, 16, and 18). The '655 patent does not indicate that these software modules are delivered to the web-based expert data center from the interface medical unit. Rather, the '655 patent indicates that the complex software modules are already located on the web-based expert data center.

Finally, U.S. patent application Ser. No. 10/438,374 (the '374 application), filed May 15, 2003, also incorporated herein by reference, provides an external device in communication with an implantable medical device. The external device may communicate with distantly located clinician equipment. The '374 application indicates that data is sent from the external device to a server, to another interface device, and finally to a general purpose personal computer (see paragraph 52 and FIG. 3).

Although the three references mentioned above teach systems and methods similar to the present invention, all of these systems and methods lack at least one critical component of the present invention: interface server software on the remote control device itself, which server software delivers data and software modules to a general purpose computer. By loading the remote control device with interface server software, a remote control device manufacturer can permit a clinician to use the remote control device to interface freely with a general purpose computer equipped with commonly available internet browser software. No pre-loaded, complex software modules are needed on the clinician's computer because all of the software modules needed to manipulate and monitor the implantable medical device are already stored on and delivered from the remote control device using interface server software. In essence, the present invention permits a clinician to use communication methods and systems—including the methods and systems of U.S. Pat. Nos. 6,442,432 and 6,497,655 and U.S. patent application Ser. No. 10/438,374—without having to purchase, stock, and operate costly interface equipment.

A simplified representation of the present invention is shown in FIG. 1. The present invention is a system for programming an implantable medical device 100 by means of a hypertext transfer protocol server, or HTTP server, located in a remote control device 110 and a general purpose computer 120. HTTP is a protocol used to request and transmit files between servers and browsers. A server is a software program located on a computer that provides some service on that computer to another computer in a network.

The implantable medical device 100 may be any combination or multiple of an electrical stimulator, an infusion pump, a sensor, or any other implantable medical device whose function can be altered by programmable commands. The remote control device 110 may be implemented in a variety of embodiments, including: a hand held remote control; an amulet; a necklace; a badge; a pin; a wrist-worn device, such as a watch or a bracelet; a talisman; or any other worn or carried device capable of performing the functions of a remote control device 110.

As shown in FIG. 2, implantable medical device 100 contains a processor 200, software 210, and telemetry means 220. Telemetry means 220 may comprise a radio frequency (RF) transmitting circuit, a magnetic coupler, or other means that allows data and commands to be transferred bidirectionally with a device external to the body of a patient. Remote control device 110 also contains a processor 230 including software 300, first telemetry means 240 for communicating with implantable medical device 100, as well as second telemetry means 250, e.g., a wired, RF, magnetic, optical, infra-red, or other telemetry means, for communicating with a network 260. The network 260 may include other computers 120 and 270, one or more servers 280, as well as other devices. Encryption and/or decryption of information may be employed by the remote control device 110, the one or more servers 280, the computer 120, and/or any other data communications device of the present invention.

As shown in FIG. 3, remote control device software 300 contains the following software modules: a device control module 310, an HTTP server software module 320, and an interface server module 330. Not shown in FIG. 3 but present within the remote control device 300 are necessary hardware components that respond to and carry out the instructions and program controls mandated by the various software modules. Such hardware components will be readily understood by one of ordinary skill in the art to be a part of the present invention. Device control module 310 is the basic control program used to communicate with the implantable medical device 100. Device control module 310 controls the operation of implantable medical device 100 (FIG. 2) based on a set of behavior or control variables, such as electrical stimulation pulse amplitude and frequency.

HTTP server software module 320 permits “server side scripts”, also called Common Gateway Interference, or CGI, scripts, to communicate to any “client” program within the reach of network 260 (FIG. 2) (wired or wireless) that supports the HTTP protocol. HTTP server software module 320 acts as a way of connecting the “server” with the “client”. Alternately, the server side scripts can act as network clients to other network devices such as printers, earphones, global positioning systems, microphones, telephones, cell phones, and modems.

Interface server module 330 manages device control module 310 variables. Interface server module 330 is identified to HTTP server software module 320 by a special symbolic address, called a Universal Resource Locator, or URL. Interface server module 330 assembles messages containing codes for hypertext markup language, or HTML, forms which are passed to a “client” browser and can be presented as documents with optional fields that can be filled with data. A “client” browser is a program that permits a computer terminal to display files and other data sent from a server.

Referring again to FIG. 2, the “client” browser is filled with files or other data from the remote control device 110 and displayed in the terminal of computer 120. Computer 120 is capable of communicating with remote control device 110 and with other computers and devices capable of communicating using HTTP protocol. Remote control device 110 is capable of communicating with computer 120 and other computers and devices capable of communicating using HTTP protocol. Computer 120 and remote control device 110 communicate using wired or wireless means, including infrared, acoustic, ultrasound, magnetic, fiberoptic, USB, Firewire, iLink, or other communication channels known by those of ordinary skill in the art.

Computer 120 must be equipped with a display program compatible with the HTTP protocol, such as a web browser program. Information in the display program can be transferred to and from other computers 270, servers 280, and other devices capable of reading and writing information in a local or general network by means of a wired, wireless, optical, satellite, or other communication channel known by those of ordinary skill in the art. For example, display applets or other configuration management information from another device located on the general network 260 may be sent to the web browser program of computer 120. Such applets may increase the aesthetics and functionality of the program displayed in the web browser. At a minimum, however, the computer 120 must be equipped with a display program compatible with the HTTP protocol. Then, all other code compatible with the HTTP protocol may be transmitted from a network to the computer 120 to increase the functionality of the computer 120. A limited amount of such code may in turn be transmitted to the remote control device 110.

Referring to FIG. 4, following are sequential steps of an embodiment of a method of operating the system of the present invention. A clinician begins at step 400 by placing the remote control device 110 within communicating range of the implantable medical device 100 and the computer 120. The clinician then continues by executing, in any preferred order, the following four steps: step 402 of activating computer 120, step 404 of activating remote control 110, step 406 of activating the wireless communications between implanted device 100 and remote control 110, and step 408 of opening a web browser within computer 120. The clinician then enters the URL for the “server side script” software of the remote control device 110 into the browser at step 410. The interface server module 330 sends a “login form” at step 412 to the browser opened in the computer 120, featuring fields for identification, password, or other security tokens. The clinician fills in the form and submits it to the interface server module 330 at step 414.

The interface server module 330 examines the filled-in form and decides if permission for display or modification of implanted device control parameters should be granted at step 416. If the permission is denied, the denial is counted at step 417. If permission has been denied, e.g., three times or less, then interface server module 330 sends an error message with a new “login form” to the browser at step 418. If permission is denied, e.g., more than three times, the interface server module sends a termination message to the browser at step 420 indicating that login attempts were unsuccessful, and the session is terminated. If the permission is granted, the interface server module 330 sends a form to the computer 120 at step 422 that is displayed in the browser with control tokens at step 424 for modifying the parameters of the remote control device 110.

At this point the clinician may modify each control variable through the browser at step 426. As the clinician modifies each control variable through the browser at step 428, a request is sent to the interface server module 330 within the remote control 110 at step 430. The interface server module 330 responds to each request from the clinician by sending out a new page displaying the control tokens for future action in the browser and the current device status at step 432. The interface server module also responds to each request from the clinician by sending the new parameters to the implantable device 100 at step 434. Alternatively, a request may be sent to the interface server module 330 to deliver all new parameters in a group to the implantable device 100 after all control variables have been modified by the clinician.

Alternately, when the clinician selects a control token for terminating the interaction at step 426, the interface server module 330 stops sending forms to computer 120 and the session terminates at step 436. Optionally, the login process may start a timer (preferably located within the remote control device 110) which specifies a maximum time for the interaction, after which the interface server module 330 stops sending out pages at optional step 438.

Once a session has begun, it is possible that errors may occur during a session that could potentially jeopardize the health of the patient. In order to avoid endangering the patient, interface server module 330 requests device control module 310 to switch the implantable medical device 100 to safe operations. Safe operations are a predefined set of parameters upon which the implantable medical device 100 can properly function without endangering the patient. By entering into safe operations, the system of the present invention limits or stops the therapy session whenever there is an error in order to ensure the safety of the patient. Safe operations continue until the clinician initiates a new session or until the error is resolved.

Additionally, information coming from computer 120 and remote control device 110 may be retrieved from arbitrary server systems on a local 290 or general network 260. Local network 290 is located entirely within a single building and is any network of any devices capable of communicating with each other and with computer 120. These portions may include pages using markup language (such as html, xml, xhtml, sgml, dhtml, and any derivative thereof), graphics, or client side logic (sometimes called scripts or applets). Markup language is a coding system used to structure, index, and link files for presentation in a browser. As a first option, remote control device 110 or the browser (under the control of an applet or script) may upload patient or device data to a server on the network. As a second option, the web page and applets may exchange data with a server 280 and/or database at a remote site on general network 260. General network 260 may include local network 290 and may also include any data transfer network of devices, such as an intranet or internet established through wired (e.g., telephone lines) and/or wireless (e.g., cell phone towers or satellite transmissions) means. Information supplied from a remote server 280 to computer 120 across the general network 260 could provide a common client desktop interface, where a clinician could see the history of the patient with other clinicians.

Network communication permits both easy file sharing and file upgrading. Information transferred over a network from a remote location is more easily upgraded than cumbersome and expensive software packages running in a clinician's office. In addition, remote server 280 or the remote database can be used to backup and clone remote control device 110 as needed.

It is thus seen that remote control device 110 provides a gateway between a physician's computer and a patient's implantable device. Remote control device 110 may further include a security device to prevent unauthorized users from impermissibly altering the parameters of a patient's implantable medical device. For example, the security device may prevent impermissible alteration by acting as a physical enabler for communication to remote control 110 that only one with possession of remote control device 110 may activate. One embodiment of such a physical enabler is a recessed switch that, when activated, enables communications with remote control device 110 for a limited time, such as 15 minutes. After the time expires, the switch is automatically deactivated and must again be activated in order for communications to continue. Other embodiments of physical enablers may include key combinations, keys and locks, and other physical security tokens.

Advantageously, both patients and clinicians, spread out over a large area, may enjoy the benefits of the present invention. The present invention permits implant patients the freedom to seek care from any able clinician equipped with a general purpose computer. Clinicians are no longer required to pay for and maintain expensive special-purpose programmers and similar complex stations to support the programming and fitting of implantable medical devices. Further, clinicians may also enjoy un-cluttering their fitting areas by reducing the number of programming systems in each area.

While the invention herein disclosed has been described by means of specific embodiments and applications thereof, numerous modifications and variations could be made thereto by those skilled in the art without departing from the scope of the invention set forth in the claims. 

1.-20. (canceled)
 21. A system, comprising: an implantable medical device; an external computer configured for transmitting a first request for service and a second request for service; and a remote control device configured for communicating with the implantable medical device, the remote control device including a server module configured for communicating with the external computer in accordance with a markup language protocol, the server module configured for sending information to the external computer in response to receiving the first request for service from the external computer, and further configured for sending operational parameters to the implantable medical device in response to receiving the second request for service from the external computer.
 22. The system of claim 21, wherein the second request for service includes the operational parameters.
 23. The system of claim 21, wherein the external computer is configured for displaying the information in a web page.
 24. The system of claim 1, wherein the information is one or more of status information pertaining to the implantable medical device, a security token, a device control token, and a communication termination control token.
 25. The system of claim 21, wherein the markup language protocol is an HTTP protocol.
 26. The system of claim 21, wherein the server module is configured for directly communicating with the external computer in accordance with the markup language protocol.
 27. The system of claim 21, wherein the each of the first and second requests for service includes a URL of the remote control device.
 28. An external control device, comprising: first telemetry circuitry configured for communicating with an implantable medical device; second telemetry circuitry configured for communicating with an external computer; and a software server module configured for communicating with a client program contained in the external computer in accordance with a markup language protocol, the server module configured for sending information to the client program in response to receiving a first request for service from the client program, and sending operational parameters to the implantable medical device in response to receiving a second request for service from the client program.
 29. The external control device of claim 28, wherein the second request for service includes the operational parameters.
 30. The external control device of claim 28, further comprising: a device control module configured for controlling the operations of the implantable medical device; and an interface server module configured for managing the device control module.
 31. The external control device of claim 28, wherein the client program is a web browser program.
 32. The external control device of claim 28, wherein the information is one or more of status information pertaining to the implantable medical device, a security token, a device control token, and a communication termination control token.
 33. The external control device of claim 28, wherein the markup language is an HTTP protocol.
 34. The external control device of claim 28, wherein the software server module is configured for sending the information directly to the client program in accordance with the markup language protocol.
 35. The external control device of claim 28, wherein the each of the first and second requests for service includes a URL of the external control device.
 36. A method of operating a system that includes an implantable medical device, a remote control device, and an external computer, the method comprising: communicating between the implantable medical device and the remote control device; sending a first request for service from the external computer to a server module of the remote control device in accordance with a markup language protocol; sending information from the server module of the remote control device to the external computer in response to the first request for service in accordance with the markup language protocol, sending a second request for service from the external computer to the server module of the remote control device in accordance with the markup language protocol; and sending operational parameters from the remote control device to the implantable medical device in response to the second request for service.
 37. The method of claim 36, wherein the second request for service includes the operational parameters.
 38. The method of claim 36, further comprising displaying the information on the external computer in a web page.
 39. The method of claim 36, wherein the information is one or more of status information pertaining to the implantable medical device, a security token, a device control token, and a communication termination control token.
 40. The method of claim 36, wherein the markup language protocol is an HTTP protocol.
 41. The method of claim 36, wherein each of the first and second requests for service includes a URL of the remote control device. 